dxp-ux

(0 reviews)

List Pricing Plans by Account

GET /pricingPlan

This usecase is used to retrieve the pricing plan details by sending account number as input.

URL
http://[localhost]:[port]/dxp-ux/v1/{businessId}/pricingPlan
URL PARAMS
nametypedescriptionrequired (mandatory-Y, optional-N, Not applicable- N/A)
businessIdstring2 letter ISO 3166 country code (PA) identifying the business unit.Y
Headers
nametypedescriptionrequired (mandatory-Y, optional-N, Not applicable- N/A)
client_idstringThe client_id identifying the channel.Y
client_secretstringPassword associated with the client_id.Y
X-Correlation-IDstringIdentifier that correlates HTTP request between a client and server. Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction.Y
Query PARAMS
nametypedescriptionrequired (mandatory-Y, optional-N, Not applicable- N/A)
identityValuestringAccount number of the customerY (CWC)
identityTypestringName of the identityValue.
Note: This should be sent as "AccountId"
Y (CWC)
includeNomServicesstringTo inculde the nominated services.
Note: This should always be sent as true
Y(CWC)
statestringstate of the plan.
Possible Values : ALL, Active
N(CWC)
Data Model - Response
field nametypedescriptionrequired (mandatory-Y, optional-N, Not applicable- N/A)
planIdstringName of the PlanY(CWC)
planNamestringdescription of the planY(CWC)
planStatusdate-timestatus of the planY(CWC)
startDatedate-timePlan start dateY(CWC)
endDatedate-timePlan end dateY(CWC)
planIsActivestringplan is active or inactiveY(CWC)
nominatedServices[]stringService associated with the planY(CWC)
nominatedServices[].serviceIdstringServiceId of the service associated with the planY(CWC)
nominatedServices[].startDatedate-timeStartDate of the service associated with the planY(CWC)
nominatedServices[].endDatestringendDate of the service associated with the planY(CWC)

Key considerations

Please find the response in the following link - DXP-UX - GET PricingPlan

Key considerations for CWC-Liberate markets

  1. PricingPlan is implemented for JM,AG,AI,VG,KY,DM,GD,MS,KN,VC,TC.
  2. planId is Name of the Plan.
  3. planName is description of the plan.
  4. planStatus is status of the plan. (possible values. W - Working, A - Allocated, B - Barred, C - Closed, D - Default)
  5. startDate is Plan start date.
  6. endDate is Plan end date.
  7. planIsActive defines plan is active or inactive.
  8. 'includeNomServices' queryParam should always be sent and it's value should be true.
  9. If the 'state' queryParam is not sent, all pricingPlans would be returned. If the 'state' queryParam is sent, it's value should always be "Active" and only active pricingPlans would be returned.

Key considerations for CWC-Cerillion markets

  1. PricingPlan is implemented for JM, BB, TT, LC, VC, GD, AG.
  2. This is applicable, if discountGroup is available for that specific BU.
  3. planId and planName would have the same value, as cerillionAPI is only returning allowanceName/planName.
  4. planStatus value is not available directly from cerillionAPI, so this would be derived based on startDate,EndDate of the plan. (possible values are "W" for Working/Active and "C" for Closed/Inactive).
  5. planIsActive value is not available directly from cerillionAPI, so this would be derived based on startDate,EndDate of the plan. (possible values are "true" or "false").
  6. 'includeNomServices' queryParam should always be sent and it's value should be true.
  7. If the 'state' queryParam is not sent, all pricingPlans would be returned. If the 'state' queryParam is sent, it's value should always be "Active" and only active pricingPlans would be returned.

Reviews